Some VBVoice applications are deployed on multiple telephony servers, in many remote locations. With a larger number of servers, control and monitoring becomes difficult, if not impossible, without some automation. The Simple Network Management Protocol (SNMP) provides a simple, yet effective solution.
In general, the SNMP model consists of a network management station and the devices that are managed. Managed devices include SNMP agents, which monitor network devices and store statistics in Management Information Bases (MIB). An MIB is a hierarchical database of objects that can be monitored and managed by a network management system.
The management application polls agents regularly to extract MIB contents. If data from an MIB does not meet or exceeds a certain criterion, an alarm is generated.
Query the network device agent
Get a response from the network device agent
Change variables in the MIB of the network device
Recognize events (traps) from a network device, such as startup, shut down, and errors
A network management station uses query / get / change commands to inspect, configure, and monitor a network device through the MIB. It uses the fourth, recognize events, to detect traps from managed devices.
Today, SNMP is supported by virtually every enterprise network equipment manufacturer worldwide.
VBVoice uses the SNMP trap mechanism to raise application level alarms that may be combined at the management station with information coming from other SNMP-aware devices, such as telephony cards, switches, and network devices, which can generate traps of their own. The general SNMP query, and get and change operations are not supported in VBVoice.
SNMP in VBVoice is part of the NLog monitoring tool and is implemented on top of the SNMP support built into Microsoft Windows. Generating a SNMP trap from VBVoice is done in two steps:
VBVoice adds an error message into the Windows NT Event Log.
The Windows NT Event Log sends the VBVoice error message to the management station as a SNMP trap.
Specifically, VBVoice errors are classified by severity into three levels, which are then translated into three Windows NT Events:
Level 1 is translated as Windows NT EventID 1001
Level 2 is translated as EventID 1002
Level 3 is translated as EventID 1003
Simply setup the windows to translate some or all of these particular events into SNMP traps. This setup procedure is done in Windows and does not involve VBVoice at all. The Windows events to SNMP trap utility allows you to choose the EventID(s) from which you want to generate SNMP traps. Read more about using this utility.
You can turn off and on the Windows NT logging from VBVoice, choose the level of severity to log, and change the level of severity for each error.
NOTE: Explanations are based on Windows 2000. For other operating systems, please refer to MSDN.
|
Read About: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|